DeadLinks in partition

SystemAdmin - Mon Jul 12 06:05:23 EDT 2010
Hello Mathias,

First, thank you for your response.

Regarding the script you are talking about, I have found it in the kitchen (Remove slate links: Fixlinks.dxl). Unfortunatly it did not solve my problem. Indeed the script looks incoming link trhough Link type which does not exist anymore.

The only way I have to detect these deadlinks is through the LinkRef type but i can not delete a LinkRef.

Morover, I can not build back the deadlinks since objects are not existing anymore.

I have looked into the dxl manual but could not find a way to delete LinkRef type. Do you have one?

Thanks in advance for you support.

Best regards,
MattMar

SystemAdmin - Mon Jul 12 06:05:23 EDT 2010
Hello Mathias,

First, thank you for your response.

Regarding the script you are talking about, I have found it in the kitchen (Remove slate links: Fixlinks.dxl). Unfortunatly it did not solve my problem. Indeed the script looks incoming link trhough Link type which does not exist anymore.

The only way I have to detect these deadlinks is through the LinkRef type but i can not delete a LinkRef.

Morover, I can not build back the deadlinks since objects are not existing anymore.

I have looked into the dxl manual but could not find a way to delete LinkRef type. Do you have one?

Thanks in advance for you support.

Best regards,
MattMar

llandale - Mon Jul 12 11:17:15 EDT 2010
If you truly cannot delete these corrupted links, then I'd be tempted to do this:
For a particular link-set containing such links...
... create a temporary link module
... find all the non-corrupt links, and create a new corresponding link in the temp link module.
... open both modules Edit, then delete the offending link-set.
... save
... re-create the formerly offending link-set.
... for each link in the temp link-set, recreate that link in the newly created link-set.
... delete the temp link module and therefore the linkset.
... save all.

• Louie

Mathias Mamsch - Mon Jul 12 11:32:07 EDT 2010
The problem is he might not even have a linkset for those links. This error occurs when the "inlinks.dtc" file from the module goes out of sync with the "treedata.dtc" files from the modules that link to you.

The solution would be to replace the "inlinks.dtc" by an empty version, but this only works a) if there are no inlinks to keep b) this must be done on database level and does not suit for a permanent process.

It sounds like a bug for sure, so probably the best way to deal with it is to try to reproduce the error, post it as a bug, try to find a workaround and wait till it gets fixed.

Regards, Mathias

llandale - Mon Jul 12 15:03:58 EDT 2010
I do not advocate playing with the database files, but if someone insisted on doing it that way, I would offer the following suggestion. Gather the list of all valid links, deleting all the links. Save and close the modules and exit DOORS. Tweak the database files. Re-open the module. Re-create the links.

• Louie

SystemAdmin - Tue Jul 13 07:01:22 EDT 2010
Dear all,

First thank you for your response and support.

Regarding your script Mathias: I have executed it and it does not print anything for the stale links :-( Indeed since the source object does not exist anymore at all.

Concernning the database manipulation: I will not touch it at all...

Regarding the linkset process, I have tried to delete the linksets and it did not delete the stale link. By the way this solution will be applied in my further processes since it seems to not add stale links.

As a conclusion for now, I guess I am screwed to have these deadlinks until the support provides a solution/bug fix if it is a bug.

Best regards,
MattMar

Mathias Mamsch - Tue Jul 13 07:40:31 EDT 2010

You can try this code with one of the affected objects as current. I forgot to use the "all" keyword. Maybe you get a printout there?

Regards, Mathias
 

Link L
LinkRef lr
 
Object obj = current
 
for lr in all (obj<-"*") do {
    ModuleVersion modVer = sourceVersion lr
    load(modVer, true) 
    string s = source lr
    int nr = sourceAbsNo lr
    print "Ref Source: " s " object nr: " nr "\n"
 
}
 
for L in all (obj<-"*") do { 
    string s = source L
    int nr = sourceAbsNo L
    print "Source: " s " object nr: " nr "\n"
}

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Mathias Mamsch - Tue Jul 13 07:40:31 EDT 2010

You can try this code with one of the affected objects as current. I forgot to use the "all" keyword. Maybe you get a printout there?

Regards, Mathias
 

Link L
LinkRef lr
 
Object obj = current
 
for lr in all (obj<-"*") do {
    ModuleVersion modVer = sourceVersion lr
    load(modVer, true) 
    string s = source lr
    int nr = sourceAbsNo lr
    print "Ref Source: " s " object nr: " nr "\n"
 
}
 
for L in all (obj<-"*") do { 
    string s = source L
    int nr = sourceAbsNo L
    print "Source: " s " object nr: " nr "\n"
}

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

SystemAdmin - Tue Jul 13 07:01:22 EDT 2010
Dear all,

First thank you for your response and support.

Regarding your script Mathias: I have executed it and it does not print anything for the stale links :-( Indeed since the source object does not exist anymore at all.

Concernning the database manipulation: I will not touch it at all...

Regarding the linkset process, I have tried to delete the linksets and it did not delete the stale link. By the way this solution will be applied in my further processes since it seems to not add stale links.

As a conclusion for now, I guess I am screwed to have these deadlinks until the support provides a solution/bug fix if it is a bug.

Best regards,
MattMar

SystemAdmin - Tue Jul 13 08:05:42 EDT 2010
Hello Mathias,

I have tested your new script and stale links information are printed in the first print "Ref source" message but not in the second one.

Regarding the solution to move the module, I can not manage to do this since I am the away partition and this module is in read only for me.

As mentioned in a previous post, the links references exist but not the links.

Best regards,
MattMar

Mathias Mamsch - Tue Jul 13 08:25:42 EDT 2010
Uhm ... Now that you mention that you are in the away partition and this module is part of it. Can anyone say if this is wanted behavior? It makes a little sense, that you see there are inlinks on the module in the home database, even though the module where the links come from has not been exported.

Regards, Mathias

SystemAdmin - Tue Jul 13 08:47:08 EDT 2010
Thanks for the support.

Regarding my database structure, both source and target modules are in the partition and I work on the away partition. I can read/write in the source module and link module and only the target module is in read only.

May be I shall return the partition to the customer and ask him to perform a purge of the link module then export the database to me in order to build back links from source to target.

In this case we should be able to definitly destroy stale links and then apply the delete linkset process to avoid new stale links.

Though, I am quite feared to manipulate database's files directly especially if I am in the away partition. Dunno what will the DOORS behaviour once the partition returned (file reference...)

Best regards,
MattMatr